Trip-based vehicle insurance

ABSTRACT

Methods and systems for offering and providing trip-based vehicle insurance are provided. Information is received regarding a vehicle operator and a vehicle, and trip-based insurance policies including quantities of vehicle use units are offered to the customer. Based on selected coverage types, the insurance provider may generate an insurance quote for a policy having an amount of the vehicle use units and may facilitate a purchase transaction with the customer for the insurance policy. Once a policy is selected and purchased, the system and method monitor vehicle use to determine each use of a vehicle use unit. Each vehicle use unit generally corresponds to one vehicle trip, but additional vehicle trip limitations may be added that may result in additional charges when exceeded during the course of a vehicle trip.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of U.S. Provisional Application No.61/775,652, filed Mar. 10, 2013, which is incorporated by referenceherein.

TECHNICAL FIELD

The present disclosure generally relates to systems and methods foroffering vehicle insurance policies, specifically offering vehicleinsurance policies where coverage is measured by the trip usage of thevehicle.

BACKGROUND

Vehicle or automobile insurance exists to provide financial protectionagainst physical damage and/or bodily injury resulting from trafficaccidents and against liability that could arise therefrom. Typically, acustomer purchases a vehicle insurance policy for a policy rate having aspecified term. In exchange for payments from the insured customer, theinsurer pays for damages to the insured which are caused by coveredperils, acts, or events as specified by the language of the insurancepolicy. The payments from the insured are generally referred to as“premiums,” and typically are paid on behalf of the insured over time atperiodic intervals. An insurance policy may remain (or have a status orstate of) “in-force” while premium payments are made during the term orlength of coverage of the policy as indicated in the policy. Aninsurance policy may “lapse” (or have a status or state of “lapsed”),for example, when premium payments are not being paid or if the insuredor the insurer cancels the policy.

Conventional vehicle insurance policies are typically based on aninsurance “term,” which specifies a fixed time period during which thecoverage in in-force (usually six months), regardless of usage duringthe time period. Some policies may be based at least in part on anestimated distance that the vehicle may travel during the term, butdistance traveled is highly variable over time. Therefore, conventionalvehicle insurance policies that are priced according to a specified termmay not accurately reflect the actual mileage or time that a vehicle isdriven, metrics that are difficult to estimate, determine, and/orverify. Other vehicle insurance policies are instead based on thedistance a vehicle travels. For example, an automobile insurance policymay be issued with a set price per mile driven. Such an insurance policymay be denominated by a certain number of miles (e.g., 5,000), just as aconventional policy may be denominated by a term of fixed duration(e.g., six months).

SUMMARY

In accordance with the described embodiments, the disclosure hereingenerally addresses vehicle insurance offered and issued based on thenumber of trips a vehicle makes. This is addressed through theintroduction of a “vehicle use unit,” which may correspond with onevehicle trip in some embodiments. In some embodiments, the vehicle useunit may be adjusted based on the time the vehicle is used, the distancethe vehicle travels, or other information collected during the vehicletrip.

Disclosed herein are methods, systems, and computer-readable mediastoring instructions for offering vehicle insurance for a vehicle. Oneembodiment consists of a computer-implemented method including receivinga vehicle identifier that identifies the vehicle and a vehicle operatoridentifier that identifies a vehicle operator, determining a cost pervehicle use unit based on the vehicle identifier and the vehicleoperator identifier, generating at least one vehicle insurance policybased on the cost per vehicle use unit, and providing an option topurchase the vehicle insurance policy to a customer associated with thevehicle.

Another embodiment consists of a computer system including acommunication module adapted to communicate data, a program memoryadapted to store non-transitory computer executable instructions, and atleast one processor adapted to interface with the communication module,wherein the processor is configured to execute the non-transitorycomputer executable instructions to cause the computer system to:receive a vehicle identifier that identifies the vehicle and a vehicleoperator identifier that identifies a vehicle operator, determine a costper vehicle use unit based on the vehicle identifier and the vehicleoperator identifier, generate at least one vehicle insurance policybased on the cost per vehicle use unit, and provide, to a customerassociated with the vehicle via the communication module, an option topurchase the vehicle insurance policy to a customer associated with thevehicle.

Yet another embodiment consists of a tangible, non-transitorycomputer-readable medium storing instructions that when executed by atleast one processor of a computer system cause the computer system toreceive a vehicle identifier that identifies the vehicle and a vehicleoperator identifier that identifies a vehicle operator, determine a costper vehicle use unit based on the vehicle identifier and the vehicleoperator identifier, generate at least one vehicle insurance policybased on the cost per vehicle use unit; and provide, to a customerassociated with the vehicle, an option to purchase the vehicle insurancepolicy.

In some embodiments, the cost per vehicle use unit includes a costassociated with a vehicle trip, comprising one or more of the following:each round trip from and back to a location; each time an engine of thevehicle is started; each time the engine of the vehicle is shut off;each time the engine of the vehicle is put into an operational state topropel the vehicle; each time the engine of the vehicle is taken out ofan operational state to propel the vehicle; each time the vehicleoperator enters the vehicle; each time the vehicle operator exits thevehicle; each time the vehicle arrives at a geographic location; eachtime the vehicle leaves a geographic location; or each time the vehicleis refueled. The cost per vehicle use unit may also include a costassociated with one or more of the following: a predetermined maximumdistance traveled by the vehicle in one vehicle trip; a predeterminedmaximum duration of vehicle operation within one vehicle trip; apredetermined maximum duration during which the engine of the vehicle isrunning in one vehicle trip; a predetermined maximum number of times theengine of the vehicle is started or shut off in one vehicle trip; apredetermined number of times the vehicle operator enter or exits thevehicle in one vehicle trip; a predetermined number of times the vehicleis near a geographic location; a predetermined maximum speed of thevehicle during the vehicle trip; a predetermined maximum revolutions perminute of the engine of the vehicle during the vehicle trip; apredetermined maximum lateral acceleration of the vehicle during thevehicle trip; a predetermined maximum longitudinal acceleration of thevehicle during the vehicle trip; a predetermined maximum number ofoccupants within the vehicle during the vehicle trip; an indication ofunsafe vehicle operation; or an indication of hazardous weatherconditions. For example, a trip on a snowy night with three teenageoccupants may cost more than a trip of equal length by a middle-agedvehicle operator on a sunny day.

In some embodiments, the systems, methods, and computer-readable mediamay also receive a selection by the customer of at least one vehicleinsurance policy and facilitate a purchase transaction with the customerfor the selected vehicle insurance policy. Additionally, someembodiments may receive a signal indicating an occurrence of the vehicletrip and record the occurrence of the vehicle trip. Recording thevehicle trip may include creating a timestamp of the occurrence,comprising one or more of a start time of the vehicle trip, an end timeof the vehicle trip, a distance traveled, a starting location of thevehicle trip, a terminal location of the vehicle trip, an indication ofunsafe vehicle operation, an indication of weather conditions, or anindication of occupants of the vehicle. In some embodiments, thesystems, methods, and computer-readable media may also determine anumber of remaining vehicle trips in the purchased vehicle insurancepolicy and automatically facilitate a purchase of additional vehicle useunits when the number of remaining vehicle use units falls below apredetermined threshold. In some embodiments, the signal indicating theoccurrence of the vehicle trip may be generated by one or more sensors.

In some embodiments, providing the option to purchase the vehicleinsurance policy to the customer may further include providing an optionto purchase at least one type of vehicle insurance coverage andproviding an option to purchase at least one quantity of vehicle useunits. In addition, some embodiments may identify an existing insurancepolicy associated with the customer and provide to the customer anoption to supplement the existing insurance policy with the vehicleinsurance policy.

Some embodiments may further receive one or more vehicle use identifiersthat identify information regarding one or more recurring uses of thevehicle by the one or more vehicle operators, including: a parkinglocation, a destination location, a route, a type of use, a time of use,a pattern of unsafe vehicle operation, a number of occupants within thevehicle, or a cargo; wherein the cost per vehicle use unit is based, atleast in part, on the one or more vehicle use identifiers.

BRIEF DESCRIPTION OF THE DRAWINGS

The figures described below depict various aspects of the applications,methods, and systems disclosed herein. It should be understood that eachfigure depicts an embodiment of a particular aspect of the disclosedapplications, systems and methods, and that each of the figures isintended to accord with a possible embodiment thereof. Furthermore,wherever possible, the following description refers to the referencenumerals included in the following figures, in which features depictedin multiple figures are designated with consistent reference numerals.

FIG. 1 illustrates a block diagram of a computer network, a computerserver, a mobile device, and an on-board computer on which an exemplarytrip-based insurance offer and purchase method and an exemplarytrip-based insurance monitoring method may be implemented in accordancewith the described embodiments;

FIG. 2 illustrates a block diagram of an exemplary client device oron-board computer;

FIG. 3 illustrates a flow diagram of an the exemplary trip-basedinsurance offer and purchase method in accordance with the presentlydescribed embodiments;

FIG. 4 illustrates a flow diagram of an exemplary trip-based insurancemonitoring method in accordance with the presently describedembodiments;

FIG. 5 illustrates a flow diagram of an exemplary trip-based insurancemonitoring method wherein the cost of each vehicle trip is determinedupon completion of the vehicle trip.

DETAILED DESCRIPTION

The systems and methods disclosed herein generally relate to processingtrip-based vehicle insurance policies, including monitoring vehicletrips to determine policy expiration. In contrast to traditionalinsurance policies, trip-based vehicle insurance policies providecoverage based at least in part upon the number of vehicle trips or usesof a vehicle. For example, a trip-based vehicle insurance policy mayinclude a quantity of vehicle use units (e.g., 50 units), therebyproviding insurance coverage for a number of vehicle trips. The vehicleuse units may further limit the vehicle trips by distance, duration,number of stops, or other metrics designed to constrain vehicle tripsfrom reaching arbitrarily long lengths. Under such a trip-based vehicleinsurance policy, the policy is charged one vehicle use unit for eachvehicle trip (or more than one unit if the vehicle trip exceeds thevehicle trip limitations set by the policy). In alternative embodiments,the vehicle use unit may correspond to a certain monetary value, andeach vehicle trip may be reviewed upon completion to determine thenumber of vehicle use units to charge the policy. For example, thetrip-based vehicle insurance policy may include a quantity of 500vehicle use units corresponding to a monetary value of $500. Uponcompletion of a vehicle trip, a cost for the vehicle trip may bedetermined (e.g., 0.65 vehicle use units for an ordinary commuter trip,2.85 vehicle use units for a late-night trip in the rain with multiplepassengers, etc.). As a variation on these alternative embodiments, thetrip-based vehicle insurance policy may not include vehicle use units assuch, but may include the purchase of a certain initial monetary valuein vehicle trips, which initial monetary value is reduced by the cost ofeach trip, as determined based upon completion of each vehicle trip asdescribed above. The policy expires when none of the purchased vehicleuse units remain to be used or when the aggregate value of the vehicletrips reaches the initial monetary value. Some policies may have anautomatic repurchase feature, such that additional vehicle use units arepurchased (or additional initial monetary values are added) if theremaining balance falls below a predetermined threshold.

Although the following text sets forth a detailed description ofnumerous different embodiments, it should be understood that the legalscope of the invention is defined by the words of the claims set forthat the end of this patent. The detailed description is to be construedas exemplary only and does not describe every possible embodiment, asdescribing every possible embodiment would be impractical, if notimpossible. One could implement numerous alternate embodiments, usingeither current technology or technology developed after the filing dateof this patent, which would still fall within the scope of the claims.

It should also be understood that, unless a term is expressly defined inthis patent using the sentence “As used herein, the term ‘______’ ishereby defined to mean . . . ” or a similar sentence, there is no intentto limit the meaning of that term, either expressly or by implication,beyond its plain or ordinary meaning, and such term should not beinterpreted to be limited in scope based on any statement made in anysection of this patent (other than the language of the claims). To theextent that any term recited in the claims at the end of this disclosureis referred to in this disclosure in a manner consistent with a singlemeaning, that is done for sake of clarity only so as to not confuse thereader, and it is not intended that such claim term be limited, byimplication or otherwise, to that single meaning. Finally, unless aclaim element is defined by reciting the word “means” and a functionwithout the recital of any structure, it is not intended that the scopeof any claim element be interpreted based on the application of 35U.S.C. §112(f).

Accordingly, as used herein, the term “vehicle” may refer to any of anumber of motorized transportation devices. A vehicle may be a car,truck, bus, train, boat, plane, motorcycle, snowmobile, other personaltransport devices, etc. As used herein, a “vehicle trip” means one useof a vehicle to travel from a departure location to a terminal location.The departure and terminal locations may be the same location, such aswhere a vehicle travels from its usual storage location to a third pointand then back to its usual storage location. The departure and terminallocations may alternatively be different locations, such as where avehicle has more than one usual storage location or where the usualstorage location is changed. The usual storage location of a vehicle mayinclude a geographic area, a port, a dock, a hangar, a parking spot, ora garage. A vehicle trip may include one or more stops along the routeof the vehicle between the departure location and the terminal location.Also as used herein, a “stop” means any point along the route of thevehicle during a vehicle trip where the vehicle trip is interrupted fora period of time, during which the vehicle's progress between thedeparture location and the terminal location is halted, other than bythe ordinary and momentary cessation of movement of the vehicle in theusual course of operation or as required by control signals, by law, orto avoid collisions. For example, a car may pause at a traffic light,stop sign, toll booth, or along a road to yield way to an emergencyvehicle without such pause being a “stop” as used herein. In variousembodiments, stops of a vehicle may be measured in a number of ways,including time, engine shut-down, or location (e.g., exiting a road orentering a dock).

Additionally, the term “insurance policy,” as used herein, generallyrefers to a contract between an insurer and an insured. In exchange forpayments from the insured, the insurer pays for damages to the insuredwhich are caused by covered perils, acts or events as specified by thelanguage of the insurance policy. The payments from the insured aregenerally referred to as “premiums,” and typically are paid on behalf ofthe insured upon purchase of the insurance policy or over time atperiodic intervals. The amount of the damages payment is generallyreferred to as a “coverage amount” or a “face amount” of the insurancepolicy. An insurance policy may remain (or have a status or state of)“in-force” while premium payments are made during the term or length ofcoverage of the policy as indicated in the policy. An insurance policymay “lapse” (or have a status or state of “lapsed”), for example, whenthe parameters of the insurance policy have expired, when premiumpayments are not being paid, when a cash value of a policy falls belowan amount specified in the policy, or if the insured or the insurercancels the policy.

The terms “insurer,” “insuring party,” and “insurance provider” are usedinterchangeably herein to generally refer to a party or entity (e.g., abusiness or other organizational entity) that provides insuranceproducts, e.g., by offering and issuing insurance policies. Typically,but not necessarily, an insurance provider may be an insurance company.

Although the embodiments discussed herein relate to vehicle orautomobile insurance policies, it should be appreciated that aninsurance provider may offer or provide one or more different types ofinsurance policies. Other types of insurance policies may include, forexample, homeowners insurance; condominium owner insurance; renter'sinsurance; life insurance (e.g., whole-life, universal, variable, term);health insurance; disability insurance; long-term care insurance;annuities; business insurance (e.g., property, liability, commercialauto, workers compensation, professional and specialty liability, inlandmarine and mobile property, surety and fidelity bonds); boat insurance;insurance for catastrophic events such as flood, fire, volcano damageand the like; motorcycle insurance; farm and ranch insurance; personalarticle insurance; personal liability insurance; personal umbrellainsurance; community organization insurance (e.g., for associations,religious organizations, cooperatives); and other types of insuranceproducts. In embodiments as described herein, the insurance providersprocess claims related to insurance policies that cover one or moreproperties (e.g., homes, automobiles, personal articles), althoughprocessing other insurance policies is also envisioned.

The terms “insured,” “insured party,” “policyholder,” and “customer” areused interchangeably herein to refer to a person, party, or entity(e.g., a business or other organizational entity) that is covered by theinsurance policy, e.g., whose insured article or entity (e.g., property,life, health, auto, home, business) is covered by the policy.

Typically, a person or customer (or an agent of the person or customer)of an insurance provider fills out an application for an insurancepolicy. In some cases, the data for an application may be automaticallydetermined or already associated with a potential customer. Theapplication may undergo underwriting to assess the eligibility of theparty and/or desired insured article or entity to be covered by theinsurance policy, and, in some cases, to determine any specific terms orconditions that are to be associated with the insurance policy, e.g.,amount of the premium, riders or exclusions, waivers, and the like. Uponapproval by underwriting, acceptance of the applicant to the terms orconditions, and payment of the initial premium, the insurance policy maybe in-force, (i.e., the policyholder is enrolled).

FIG. 1 illustrates a block diagram of an exemplary trip-based insurancesystem 100 on which the exemplary trip-based insurance offer andpurchase method 300 and the exemplary trip-based insurance monitoringmethod 400 may be implemented. The high-level architecture includes bothhardware and software applications, as well as various datacommunications channels for communicating data between the varioushardware and software components. The trip-based insurance system 100may be roughly divided into front-end components 102 and back-endcomponents 104. The front-end components 102 may present information toand receive information from a vehicle operator, client device user, orcustomer and monitor the use of a vehicle 108 (e.g., a car, truck,motorcycle, etc.) by the vehicle operator. The user may interact withthe system 100 using a client device 110 (e.g., a smart phone, a tabletcomputer, a desktop computer, a special purpose computing device, etc.),which may be communicatively connected to an on-board computer 114. Tomonitor the vehicle 108, the front-end components 102 may include one ormore sensors (not shown) installed within the vehicle 108 that maycommunicate with the client device 110 or an on-board computer 114. Thefront-end components 102 may further process the sensor data using theclient device 110 or on-board computer 114 to determine when a vehicletrip occurs. In some embodiments of the system, the front-end components102 may communicate with the back-end components 104 via a network 130.The back-end components 104 may use one or more servers 140 to receivedata from the user or sensors from the front-end components 102,determine insurance policies to present to the user, facilitate thepurchase of an insurance policy, and monitor the vehicle 108 for useunder the insurance policy. A record of usage of the vehicle 108 may bestored either in the front-end components or in the back-end componentsvia network 130.

The front-end components 102 may be disposed within one or more clientdevices 110 or on-board computers 114, which may be permanently orremovably installed in the vehicle 108. The client device 110 or theon-board computer 114 may interface with one or more sensors (not shown)within the vehicle 108 (e.g., an ignition sensor, an odometer, a systemclock, a speedometer, a tachometer, an accelerometer, a gyroscope, acompass, etc.), which sensors may also be incorporated within orconnected to the client device 110 or the on-board computer 114. In someembodiments, the client device 110 may be a specialized computing devicedesigned to monitor and record vehicle usage, either independently or inconjunction with the on-board computer 114. The on-board computer 114may supplement the functions performed by the client device 110described herein by, for example, sending or receiving information toand from the client device 110 or the sensors (not shown). In oneembodiment, the on-board computer 114 may perform all of the functionsof the client device 110 described herein, in which case no clientdevice 110 may be present in the system 100. In another embodiment, theclient device 110 may perform all of the functions of the on-boardcomputer 114, in which case no on-board computer 114 may be present inthe system 100. Either or both of the client device 110 or on-boardcomputer 114 may communicate with the network 130 over links 112 and118, respectively. Additionally, the client device 110 and on-boardcomputer 114 may communicate with one another directly over link 116.

The client device 110 may be either a general-use personal computer,cellular phone, smart phone, tablet computer, or a dedicated vehicle usemonitoring device. Although only one client device 110 is illustrated,it should be understood that a plurality of client devices 110 may beused in some embodiments. Particularly, one client device 110 (e.g., adesktop computer) may be used to implement the trip-based insuranceoffer and purchase method 300, while another client device 110 (e.g., asmart phone or dedicated vehicle use monitoring device) may be used toimplement the trip-based insurance monitoring method 400. The on-boardcomputer 114 may be a general-use on-board computer capable ofperforming many functions relating to vehicle operation or a dedicatedcomputer for monitoring vehicle usage. Further, the on-board computer114 may be installed by the manufacturer of the vehicle 108 or as anaftermarket modification to the vehicle 108. In some embodiments, theclient device 110 or on-board computer 114 may be thin-client devicesthat outsource some or most of the processing to the server 140.

In some embodiments, the front-end components 102 communicate with theback-end components 104 via the network 130. The network 130 may be aproprietary network, a secure public internet, a virtual private networkor some other type of network, such as dedicated access lines, plainordinary telephone lines, satellite links, cellular data networks,combinations of these, etc. Where the network 130 comprises theInternet, data communications may take place over the network 130 via anInternet communication protocol. The back-end components 104 include oneor more servers 140. Each server 140 may include one or more computerprocessors adapted and configured to execute various softwareapplications and components of the trip-based insurance system 100, inaddition to other software applications. The server 140 may furtherinclude a database 146, which may be adapted to store data related tothe operation of the trip-based insurance system 100. Such data mightinclude, for example, date and times of vehicle use, duration of vehicleuse, distance traveled by the vehicle 108 in each use, speed of thevehicle 108, RPM or other tachometer readings of the vehicle 108,lateral and longitudinal acceleration of the vehicle 108, number andlocation of stops made by the vehicle 108 during each use, or other datarelating to use of the vehicle 108, the vehicle operator, or the vehicleinsurance policy, which may be uploaded to the server 140 via thenetwork 130. The server 140 may access data stored in the database 146when executing various functions and tasks associated with the operationof the trip-based insurance system 100.

Although the trip-based insurance system 100 is shown to include onevehicle 108, one client device 110, one on-board computer 114, and oneserver 140, it should be understood that different numbers of vehicles108, client devices 110, on-board computers 114, and servers 140 may beutilized. For example, the system 100 may include a plurality of servers140 and hundreds of client devices 110 or on-board computers 114, all ofwhich may be interconnected via the network 130. Furthermore, thedatabase storage or processing performed by the one or more servers 140may be distributed among a plurality of servers 140 in an arrangementknown as “cloud computing.” This configuration may provide variousadvantages, such as enabling near real-time uploads and downloads ofinformation as well as periodic uploads and downloads of information.This may in turn support a thin-client embodiment of the client device110 or on-board computer 114 discussed herein.

The server 140 may have a controller 155 that is operatively connectedto the database 146 via a link 156. It should be noted that, while notshown, additional databases may be linked to the controller 155 in aknown manner. For example, separate databases may be used for vehicleoperator information, vehicle insurance policy information, and vehicleuse information. The controller 155 may include a program memory 160, aprocessor 162 (which may be called a microcontroller or amicroprocessor), a random-access memory (RAM) 164, and an input/output(I/O) circuit 166, all of which may be interconnected via anaddress/data bus 165. It should be appreciated that although only onemicroprocessor 162 is shown, the controller 155 may include multiplemicroprocessors 162. Similarly, the memory of the controller 155 mayinclude multiple RAMs 164 and multiple program memories 160. Althoughthe I/O circuit 166 is shown as a single block, it should be appreciatedthat the I/O circuit 166 may include a number of different types of I/Ocircuits. The RAM 164 and program memories 160 may be implemented assemiconductor memories, magnetically readable memories, or opticallyreadable memories, for example. The controller 155 may also beoperatively connected to the network 130 via a link 135.

The server 140 may further include a number of software applicationsstored in a program memory 160. The various software applications mayinclude a client application 142 for implementing the trip-basedinsurance offer and purchase method 300 or the trip-based insurancemonitoring method 400 on the server 140. The software applications mayfurther include a web server application 143 responsible for generatingdata content to be included in web pages sent from the web server 140 tothe client device 110 or on-board computer 114. The various softwareapplications may be executed on the same computer processor as theclient application 142 or the web server application 143, or thesoftware application may be executed on different computer processors.

FIG. 2 illustrates a block diagram of an exemplary client device 110 oran exemplary on-board computer 114 consistent with the system 100. Theclient device 110 or on-board computer 114 may include a display 202, aGlobal Positioning System (GPS) unit 206, a communication unit 220, oneor more additional sensors (not shown), a user-input device (not shown),and, like the server 140, a controller 204. In some embodiments, theclient device 110 and on-board computer 114 may be integrated into asingle device, or either may perform the functions of both. Functionsperformed by either the client device 110 or the on-board computer 114may also be performed by the client device 110 in concert with theon-board computer 114.

When implementing the trip-based insurance offer and purchase method300, the controller 204 may communicate with the server 140 to provideinformation regarding the vehicle operator or the vehicle 108. Theclient device 110 or the on-board computer 114 may further receiveinformation regarding one or more vehicle insurance policies, includingtrip-based insurance policies, from the server 140 and display theinformation to the user using the display 202 or other means. The clientdevice 110 or the on-board computer 114 may also receive selections ofpolicy options from the user and communicate with the server 140 via thenetwork 130 to facilitate a purchase of one or more vehicle insurancepolicies. In some embodiments, communication between the controller 204and the server 140 may include the use of the communication unit 220.Additionally, or alternatively, the client device 110 or the on-boardcomputer 114 may communicate with the server 140 to transmit or receiveinformation regarding vehicle usage or the vehicle insurance policy(e.g., average trip length, remaining trips in the policy, etc.).

When implementing the trip-based insurance monitoring method 400, thecontroller 204 may receive sensor data, determine vehicle usage, andcommunicate information regarding vehicle trips to the server 140.Sensor data regarding vehicle usage may come from the GPS unit 206 orother sensors (not shown) incorporated within the client device 110 oron-board computer 114. Additionally, or alternatively, the communicationunit 220 may receive sensor data from one or more external sensors (notshown) within the vehicle 108. The sensor data may be processed by thecontroller 204 to determine vehicle usage. Additionally, the controller204 may determine information regarding vehicle usage (e.g., triplength, trip duration, average speed, acceleration, etc.). Additionally,or alternatively, the client device 110 or on-board computer 114 maytransmit the sensor data to the server 140 for processing or may receiveinformation from the server 140 for presentation to the vehicle operatorvia the network 130 (e.g., remaining trips in the vehicle insurancepolicy).

Similar to the controller 155, the controller 204 includes a programmemory 208, one or more microcontrollers or microprocessors (MP) 210, aRAM 212, and an I/O circuit 216, all of which are interconnected via anaddress/data bus 214. The program memory 208 includes an operatingsystem 226, a data storage 228, a plurality of software applications230, and a plurality of software routines 234. The operating system 226,for example, may include one of a plurality of mobile platforms such asthe iOS®, Android™, Palm® webOS, Windows® Mobile/Phone, BlackBerry® OS,or Symbian® OS mobile technology platforms, developed by Apple Inc.,Google Inc., Palm Inc. (now Hewlett-Packard Company), MicrosoftCorporation, Research in Motion (RIM), and Nokia, respectively. The datastorage 228 may include data such as user profiles and preferences,application data for the plurality of applications 230, routine data forthe plurality of routines 234, and other data necessary to interact withthe server 140 through the digital network 130. In some embodiments, thecontroller 204 may also include, or otherwise be communicativelyconnected to, other data storage mechanisms (e.g., one or more hard diskdrives, optical storage drives, solid state storage devices, etc.) thatreside within the client device 110 or on-board computer 114.

As discussed with reference to the controller 155, it should beappreciated that although FIG. 2 depicts only one microprocessor 210,the controller 204 may include multiple microprocessors 210. Similarly,the memory of the controller 204 may include multiple RAMs 212 andmultiple program memories 208. Although the FIG. 2 depicts the I/Ocircuit 216 as a single block, the I/O circuit 216 may include a numberof different types of I/O circuits. The controller 204 may implement theRAMs 212 and the program memories 208 as semiconductor memories,magnetically readable memories, or optically readable memories, forexample.

The communication unit 220 may communicate with one or more externalsensors (not shown) within the vehicle 108, client devices 110, on-boardcomputers 114, or servers 140 via any suitable wireless communicationprotocol network, such as a wireless telephony network (e.g., GSM, CDMA,LTE, etc.), a Wi-Fi network (802.11 standards), a WiMAX network, aBluetooth network, etc. Additionally, or alternatively, thecommunication unit 220 may also be capable of communicating using a nearfield communication standard (e.g., ISO/IEC 18092, standards provided bythe NFC Forum, etc.). Furthermore, the communication unit 220 mayprovide input signals to the controller 204 via the I/O circuit 216. Thecommunication unit 220 may also transmit sensor data, device statusinformation, control signals, or other output from the controller 204 toone or more external sensors within the vehicle 108, client devices 110,on-board computers 114, or servers 140.

The GPS unit 206 may use “Assisted GPS” (A-GPS), satellite GPS, or anyother suitable global positioning protocol (e.g., the GLONASS systemoperated by the Russian government) or system that locates the positionof the client device 110 or on-board computer 114. For example, A-GPSutilizes terrestrial cell phone towers or Wi-Fi hotspots (e.g., wirelessrouter points) to more accurately and more quickly determine location ofthe client device 110 or on-board computer 114, while satellite GPSgenerally is more useful in more remote regions that lack cell towers orWi-Fi hotspots. The GPS unit 206 and the one or more other sensors (notshown) may be referred to collectively as the “sensors” of the clientdevice 110 or on-board computer 114. Of course, it will be appreciatedthat additional GPS units 206 may be added to the client device 110 oron-board computer 114.

The user-input device (not shown) may include a “soft” keyboard that isdisplayed on the display 202 of the client device 110 or on-boardcomputer 114, an external hardware keyboard communicating via a wired ora wireless connection (e.g., a Bluetooth keyboard), an external mouse, amicrophone, or any other suitable user-input device. The user-inputdevice (not shown) may also include a microphone capable of receivinguser voice input.

The one or more processors 210 may be adapted and configured to executeany of one or more of the plurality of software applications 230 or anyone or more of the plurality of software routines 234 residing in theprogram memory 204, in addition to other software applications. One ofthe plurality of applications 230 may be a client application 232 thatmay be implemented as a series of machine-readable instructions forperforming the various tasks associated with implementing part or all ofthe trip-based insurance offer and purchase method 300 or the trip-basedinsurance monitoring method 400, discussed below, as well as receivinginformation at, displaying information on, and transmitting informationfrom the client device 110 or on-board computer 114. One of theplurality of applications 230 may be a native web browser 236, such asApple's Safari®, Google Android™ mobile web browser, Microsoft InternetExplorer® for Mobile, Opera Mobile™, that may be implemented as a seriesof machine-readable instructions for receiving, interpreting, anddisplaying web page information from the server 140. Another applicationof the plurality of applications may include an embedded web browser 242that may be implemented as a series of machine-readable instructions forreceiving, interpreting, and displaying web page information from theserver 140. One of the plurality of routines may include a vehicleinsurance purchase routine 238 corresponding to part or all of thetrip-based insurance offer and purchase method 300. The vehicleinsurance purchase routine 238 may receive information from the user andcommunicate with the serve 140 via the network 130 to facilitate theselection and purchase of one or more vehicle insurance policies.Another routine in the plurality of routines may include a vehicle tripmonitoring routine 240 corresponding to part or all of the trip-basedinsurance monitoring method 400. The vehicle trip monitoring routine 240may process data from the sensors to determine and record the occurrenceof a vehicle trip under the terms of the insurance policy.

A user may launch the client application 232 from the client device 110or on-board computer 114 to access the server 140 to implement part orall of the trip-based insurance offer and purchase method 300 or thetrip-based insurance monitoring method 400. Additionally, the user mayalso launch or instantiate any other suitable user interface application(e.g., the native web browser 236, or any other one of the plurality ofsoftware applications 230) to access the server 140 to realize part orall of the trip-based insurance offer and purchase method 300 or thetrip-based insurance monitoring method 400.

In embodiments where the client device 110 or on-board computer 114 is athin-client device, the server 140 may perform many of the processingfunctions remotely that would otherwise be performed by the clientdevice 110 or on-board computer 114. In such embodiments, the clientdevice 110 or on-board computer 114 may receive data from the user orfrom the sensors and transmit the data to the server 140 for remoteprocessing via the network 130.

FIG. 3 is a flow diagram depicting an exemplary embodiment of atrip-based insurance offer and purchase method 300, which may beimplemented by the trip-based insurance system 100. More particularlythe method 300 may be performed by the server 140, in some parts bycommunication with the client device 110. The client device 110 mayinitiate the method 300 by a command from the user via the clientapplication 232, native web browser 236, the embedded web browser 242,or other means of establishing a communication connection between theclient device 110 and the server 140. The server 140 receivesinformation from the user at block 302, identifies any current policieslinked to the user, vehicle operator, or vehicle 108 at block 304,determines a cost per vehicle use unit at block 306, and determinespolicy premiums for at least one vehicle insurance policy at block 308.The server 140 then provides one or more vehicle insurance policies tothe user at block 310, receives a selection from the user at block 312,and facilitates a purchase of the selected vehicle insurance policy orpolicies at block 314. Once the vehicle insurance policy is in force,the server 140 monitors vehicle use to determine the number of vehicleuse units used at block 316, determines the number of remaining vehicleuse units based on the policy coverage at block 318, and determineswhether the number of remaining vehicle use units is less than athreshold number at block 320. When the server 140 determines that thenumber of remaining vehicle use units is less than the threshold atblock 320, it may further determine at block 322 whether the vehicleinsurance policy is configured for automatic renewal. If the vehicleinsurance policy is not configured for automatic renewal, the server 140may cause a renewal reminder to be generated and provided to the user atblock 324. If the vehicle insurance policy is configured for automaticrenewal, the server 140 may facilitate an additional purchase of vehicleuse units at block 326, following which the server 140 may continue tomonitor vehicle use at block 316.

Following the initiation of the method 300, the server 140 may requestand receive information from the user at block 302. This may include arequest from the server 140 to the client device 110 for informationrelevant to the actuarial determination of policy rates, particularlyvehicle operator information, customer information, vehicle information,and vehicle use information. In some embodiments, the server 140 mayrequest information from the user of the client device 110 in one ormore series of questions, some of which may include suggested responsesbased on information retrieved from the system database 146.Alternatively, the user may provide information to the server 140 inresponse to a series of prompts generated by the client application 232,or the user may select information to provide to the server 140. Thevehicle operator information may include information regarding thevehicle operator (and, where different, the customer or user of theclient device 110), such as the vehicle operator's name, date of birth,residence, operator's license ID number and issuing entity, priorinsurance coverage, prior operating history (e.g., length of timelicensed, accidents, damage, claims, etc.), associated vehicles,criminal history, financial history, or other relevant informationregarding the vehicle operator. Where the customer is a separate entityfrom the vehicle operator, additional information regarding the customermay be requested or received, including the customer's vehicles,operations, insurance policies, insurance history, claims history,creditworthiness, or other relevant information regarding the customer.The vehicle information may include a vehicle type, registration number,registering entity, vehicle maker, vehicle model, vehicle year, vehiclemileage, vehicle time in operation, vehicle configuration, vehiclecondition, standard or additional equipment installed in the vehicle,vehicle license plate number and issuing entity, one or more addressesassociated with the vehicle (e.g., garaging address), or otherinformation relating to the vehicle 108. Additionally, the vehicle useinformation may include typical routes traveled, typical timing ofvehicle operation, frequently visited locations, driving patterns orhabits of the vehicle operator (e.g., hard braking, excessiveacceleration, lateral swerving, maintaining insufficient distance fromother vehicles, insufficient mirror checking, excessive time lookingaway from the direction of vehicle travel, etc.), typical trip length,typical trip duration, frequency of stops during trips, typical numberof stops during trips, typical passengers or cargo transported, or otherinformation relating to vehicle usage. The information may be entered bythe user into the client device 110 and transmitted to the server 140via the network 130.

Using the information received in block 302, the server 140 may attemptto identify any existing policies associated with the customer, vehicle108, or vehicle operator. For example, the server 140 may determine thatthe vehicle 108 is covered under an existing trip-based vehicleinsurance policy or under a traditional, time-based insurance policy forthe customer but not for the identified vehicle operator. As anotherexample, the server 140 may identify a homeowner's policy or anotherinsurance policy associated with the vehicle operator. As a furtherexample, the server 140 may identify a vehicle insurance policy of thevehicle operator covering another vehicle 108 located at the same or adifferent address. Where an existing policy is identified that may becombined with trip-based insurance, the server 140 may generate arequest to the user to select whether to add coverage to an existingpolicy or to create a new policy. For example, a user may have anexisting traditional vehicle insurance policy covering a first vehicleand a separate trip-based insurance policy covering a second vehicle.The server 140 may generate a request to the user to choose whether theuser would like to add a new trip-based insurance policy or addadditional trip-based insurance to the existing policies. In someembodiments, the identification of one or more existing insurancepolicies may also affect the cost per use unit determined in block 306.

With the information received and identified in block 302 and 304, theserver 140 may determine one or more costs per vehicle use unit at block306. The cost per vehicle use unit may be a rate charged to insure thevehicle 108 during a vehicle trip or some portion thereof. For example,the cost per vehicle unit may be a fee (e.g., $2.22, $5.87, etc.) for alevel of insurance coverage (e.g., state minimum liability coverage,collision coverage up to $10,000 with a $500 deductible, etc.) that isin force only for the duration of the vehicle trip. In some embodiments,a number of costs per vehicle use unit may be determined, eachcorresponding to a policy coverage level (e.g., $150,000 liabilitycoverage with a $5,000 deductible, $250,000 liability coverage with nodeductible, etc.). For example, one cost per vehicle use unit may covervehicle trips for commuting (e.g., 30 miles round-trip on over 12 hourson weekdays) and another cost per vehicle use unit may cover vehicletrips for leisure (e.g., 150 miles round-trip over 48 hours). As anotherexample, the user may purchase roadside assistance coverage only onvehicle trips longer than 50 miles or that take the vehicle more than 20miles from home. Alternatively, the user may pre-select a policycoverage level for which the server 140 may then determine one or morecosts per vehicle use unit. The cost per vehicle use unit may dependupon any of the information received at block 302, as well asinformation regarding the vehicle operator or the vehicle 108 obtainedfrom other sources. Such other sources of information may includerecords in the system database 146, police or other official records,court records, credit agency records, or reports of third-party dataproviders. The cost per vehicle use unit for any policy coverage leveland use unit may be determined from the information received or obtainedby the application of known methods of actuarial analysis.

In some embodiments, each vehicle use unit may correspond exactly to avehicle trip, such that every vehicle trip uses one and only one vehicleuse unit of the vehicle insurance policy. In other embodiments, eachvehicle use unit may be limited by one or more additional metrics, suchas time, duration, or stops. In a variety of embodiments, one or more ofthe following vehicle trip limitations may be included: a predeterminedmaximum distance traveled by the vehicle in one vehicle trip; apredetermined maximum duration of vehicle operation within one vehicletrip; a predetermined maximum duration during which the engine of thevehicle is running in one vehicle trip; a predetermined maximum numberof times the engine of the vehicle is started or shut off in one vehicletrip; a predetermined number of times the vehicle operator enter orexits the vehicle in one vehicle trip; a predetermined number of timesthe vehicle is near a geographic location; a predetermined maximum speedof the vehicle during the vehicle trip; a predetermined maximumrevolutions per minute of the engine of the vehicle during the vehicletrip; a predetermined maximum lateral acceleration of the vehicle duringthe vehicle trip; a predetermined maximum longitudinal acceleration ofthe vehicle during the vehicle trip; or a predetermined maximum numberof occupants within the vehicle during the vehicle trip. For example,vehicle use units may be time-limited, such that a vehicle tripexceeding a predetermined time threshold (e.g., 2 hours, 24 hours, etc.)is recorded as using more than one vehicle use unit. In another example,a vehicle trip may incur the use of an additional vehicle use unit ifthe vehicle 108 passes a location more than a predetermined number oftimes, such as where the vehicle 108 makes multiple deliveries from acentral location in a number of separate segments but where the centrallocation is not a departure location of a vehicle trip (e.g., deliveriesfrom a pizzeria).

In some embodiments, the vehicle trip limitations may be used by theserver 140 to adjust the number of vehicle use units charged for avehicle trip that exceeds the vehicle trip limitation threshold orthresholds. For example, a vehicle trip of 300 miles may incur a chargeof two vehicle use units where a vehicle trip limitation of 200 miles isincluded in the vehicle use units. Alternatively, fractional vehicle useunits may be used, such that only one and a half vehicle use units arecharged in the preceding example. In other embodiments, a surcharge oradditional premium rate may apply to vehicle trips that exceed thethresholds of the vehicle trip limitations. For example, a vehicleinsurance policy may provide for a cost per vehicle use unit of $3.33with a vehicle trip limitation of 60 miles and an additional premium of$0.12 per mile beyond the vehicle trip limitation.

In some embodiments, a vehicle trip may incur the use of additionalvehicle use units or a monetary surcharge for unsafe vehicle operation,such as hard braking, excessive lateral or longitudinal acceleration,instances of RPM measurements above a threshold, vehicle swerving,measures of distraction or drowsiness, or other indications of unsafevehicle operation based on telemetric or biometric measurements. Forexample, the vehicle trip may be analyzed upon completion, and asurcharge (e.g., 0.05 vehicle use units, $0.07, etc.) may be added foreach recorded instance of hard braking. Additionally, a surcharge may beadded for vehicle trips occurring at hazardous times or during inclementweather conditions.

Additionally, or alternatively, in some embodiments, vehicle trips thatfail to meet a predetermined minimum threshold for duration, distance,or other metrics may be covered without incurring the use of a vehicleuse unit. For example, the vehicle insurance policy may not be chargedthe use of one vehicle use unit where a vehicle engine operates for lessthan a minute or where the vehicle moves less than twenty feet. This mayreduce the number of false determinations of the occurrence of a vehicletrip, such as may occur where, for example, the vehicle 108 is startedsolely to operate a powered feature of the vehicle 108, such as openingor closing windows.

In some embodiments, one or more costs per vehicle use unit may also bedetermined based upon the vehicle trip limitations discussed above. Theserver 140 may process the information received from the user in block302 to determine sets of costs per vehicle use unit that vary dependingupon both policy coverage levels and vehicle trip limitations. Forexample, a first cost per vehicle use unit may be determined thatcorresponds to a vehicle trip limitation of two hours, and a second costper vehicle use unit may be determined that corresponds to a vehicletrip limitation of twenty-four hours. Similarly, a third cost pervehicle use unit may be determined that corresponds to a vehicle triplimitation of two hours and a vehicle trip limitation of thirty miles.In some embodiments, a recommended set of vehicle trip limitations(e.g., thresholds of fifty miles, two operating hours, twelve totalhours, and three stops) may be determined by the server 140 based uponthe vehicle use information received at block 302. In embodiments inwhich the vehicle trips will be individually analyzed upon completion todetermine cost based on the trip characteristics, determination of thecost per vehicle trip in block 306 may include calculation of the costsa number of exemplary vehicle trips. The one or more costs per vehicleuse unit determined at block 306 may be presented to the user or may beincorporated within policy premiums for one or more vehicle insurancepolicies offered to the user.

The server 140 may further determine one or more policy premiums for oneor more vehicle insurance policies at block 308. In addition totrip-based vehicle insurance policies, in some embodiments, the vehicleinsurance policies may include time-based vehicle insurance policies,distance-based vehicle insurance policies, or any combination of theseor other types of vehicle insurance policies. Policy premiums forvehicle insurance policies not including trip-based vehicle insurancemay be determined by the server 140 using established actuarial methodsbased upon the information received at block 302. Policy premiums forvehicle insurance policies including trip-based vehicle insurance maycombine traditionally determined premium components (e.g., a fixedpremium for a level of comprehensive vehicle insurance coverage for afixed period of time) with premiums determined for one or morequantities of vehicle use units (e.g., 50 trips, 100 trips). Similarly,pure trip-based vehicle insurance policy premiums may be determined bythe product of the cost per vehicle use unit and the quantity of vehicleuse units, which premium may be adjusted in some embodiments (e.g., byapplying a discount to policies with quantities of vehicle use unitsabove a set level). In some embodiments, the policy premiums may includea schedule of charges for unsafe vehicle operation or vehicle operationunder hazardous conditions, in addition to one or more baseline costsper vehicle trip.

The server 140 may then provide one or more vehicle insurance policiesto the user at block 310. This may include transmitting informationregarding the one or more vehicle insurance policies (e.g., terms,descriptions, explanations, premiums, etc.) from the server 140 to theclient device 110 via the network 130. The client device 110 may thenuse the display 202 to present the policy options to the user, which mayinclude one or more quantity options for vehicle use units. Theinformation provided to the user may include options for one or moretypes of traditional or trip-based vehicle insurance coverage, one ormore classes of coverage levels (e.g., standard, economy, minimumrequired, etc.), one or more coverage levels, one or more deductiblelevels, one or more types of vehicle use units corresponding to sets ofvehicle trip limitations, one or more quantities of vehicle use units,and cost or policy premium information relating to any of the policy andquantity options.

The client device 110 may be configured to allow the user to select oneor more vehicle insurance policy options and quantities using an inputdevice (not shown). In some embodiments, the client application 232 orthe vehicle insurance purchase routine 238 may prompt the user to selectone or more policy or quantity options or may receive user selectionsfrom among the options provided in block 310. The client device 110 maycommunicate the vehicle insurance policy and vehicle use unit quantityselections of the user to the server 140 via the network 130 at block312. Alternatively, or additionally, in some embodiments, the server 140may provide a range of vehicle insurance policy options to be presentedto the user and receive a selection of one or more types of policiesprior to determining the cost per vehicle use unit or the policypremiums or prior to providing the policy and quantity options asdiscussed above.

Upon receiving the user selections at block 312, the server 140 mayfacilitate a purchase of the one or more selected vehicle insurancepolicies selected by the user at block 314. The purchase may befacilitated by any of the various known techniques, including receivingan electronic payment from the user, receiving a purchase order to beinvoiced, or generating a purchase order number for the customer to usein completing the purchase at a physical office location, by telephone,or otherwise. Upon confirmation or completion of the order, the server140 may provide the user with additional required or optionaldocumentation regarding the purchased vehicle insurance policy,including proof of insurance.

Once the trip-based vehicle insurance policy has been purchased and isin force, the server 140 may continue to monitor vehicle use at block316 to identify and record each vehicle trip. Monitoring use of thevehicle 108 may be performed by communication with the client device110, the on-board computer 114, or a dedicated monitoring device. Insome embodiments, the dedicated monitoring device may be removably orirremovably installed within the vehicle 108. In other embodiments, thededicated monitoring device may include a sensor that detects when thevehicle 108 is near a location (e.g., in a garage or driveway, over amat placed on a parking spot, etc.) that serves as the departurelocation and terminal location of the vehicle trips. The sensor maycommunicate with the client device 110, the on-board computer 114, orthe server 140 in some embodiments, and the sensor may consist of anyknown techniques for sensing the presence of a vehicle (e.g., infraredsensing, magnetic sensing, proximity sensing, etc.).

When the client device 110, on-board computer 114, or dedicatedmonitoring device determines the occurrence of a vehicle trip, it mayfurther record information regarding the vehicle trip. The informationmay be transmitted to the server 140 either as it is recorded or at alater point (e.g., at the completion of the vehicle trip), and theserver 140 may further record the information in the system database146. Such information may include a timestamp corresponding to thevehicle trip, a start time of the vehicle trip, an end time of thevehicle trip, a distance traveled, a starting location of the vehicletrip, or a terminal location of the vehicle trip. The server 140 mayfurther receive and record information regarding the vehicle operation,including vehicle speed, number of stops, measurements of accelerationduring the vehicle trip, indications of swerving or hard braking,weather conditions during the trip, vehicle occupants, or otherinformation regarding the operation of the vehicle 108 at block 316.

FIGS. 4 and 5 illustrate flow diagrams of exemplary methods formonitoring vehicle use at block 316. FIG. 4 illustrates a flow diagramof a trip-based insurance monitoring method 400 that may operate tomonitor vehicle use at block 316 to track each use of a vehicle use unitof the trip-based vehicle insurance policy. The method 400 may beimplemented by the client device 110, on-board computer 114, dedicatedmonitoring device (not shown), or by the server 140 receivinginformation from any of these. For clarity, the following discussionrefers to an embodiment in which the client device 110 implements themethod 400 and communicates with the server 140 only at the completionof the vehicle trip, but it should be understood that any of thepreviously mentioned configurations may instead implement the method400.

The method 400 begins at block 402 when the client device 110 receivesan indication of the start of a vehicle trip. The indication may includeone or more of the following: movement of the vehicle 108 from alocation the vehicle is stored; starting the engine of the vehicle 108;putting the engine of the vehicle 108 into an operational state topropel the vehicle; entry of the vehicle operator into the vehicle 108;or placement of the dedicated monitoring device within or in proximityto the vehicle 108. Additionally, or alternatively, the indication mayinclude receiving input from the user indicating the start of a vehicletrip, such as by interacting with the client application 232 on theclient device 110. For example, the client device 110 may identify acommunication connection (e.g., via Bluetooth pairing) with the vehicle108 and receive an indication from its GPS unit 206 that the clientdevice 110 has moved to a new location while remaining communicativelyconnected to the vehicle 108. As another example, the on-board computer114 may determine that the vehicle 108 has been removed beyond range ofcommunication with a fixed-location component installed at a usualstorage location of the vehicle 108 (e.g., an RFID tag or beacon placedat the entrance of a garage) and communicate this information to theclient device 110. In some embodiments, receiving an indication of thestart of a vehicle trip may cause the client device 110 or the on-boardcomputer 114 to run the vehicle trip monitoring routine 240. Inalternate embodiments, the vehicle 108 may be continuously monitored, inwhich case the occurrence of a vehicle trip may be indicated at eitherthe start or end of the vehicle trip.

Upon receiving an indication of the start of the vehicle trip at block402, the client device 110 may record a time stamp associated with thestart of the vehicle trip at block 404. The time stamp may include thedate, time of day, location, or other information related to the vehicletrip. The time stamp may be further associated with additionalinformation during or upon completion of the vehicle trip, including thefollowing: distance traveled, duration of the vehicle trip, duration ofvehicle operation during the vehicle trip (e.g., excluding stops),terminal location of the vehicle trip, unsafe vehicle operation (e.g.,hard braking, excessive acceleration, lateral swerving, etc.), weatherconditions, vehicle occupants, or time, duration, and location of stops.

At the start of the trip, in some embodiments, the client device 110 mayreset the values of one or more counters relating to the trip distance,the trip time (e.g., duration of the trip or time of actual vehicleoperation), and the trip stops at block 406. Alternatively, this blockmay be excluded from the method 400 in other embodiments, particularlywhere the distance, time, and stops may be recalculated on a periodic orcontinuous basis throughout the vehicle trip.

The client device 110 may then proceed to monitor the vehicle triplimitations while the vehicle trip is in progress. The vehicle trip maybe determined to be complete at block 408 upon the occurrence of one ormore of the following: the return of the vehicle 108 to its startinglocation; the arrival of the vehicle 108 at another usual storagelocation; the engine of the vehicle 108 is shut off; the vehicle istaken out of an operational state to propel the vehicle 108; the vehicleoperator exits the vehicle 108; the vehicle 108 is refueled.Additionally, or alternatively, the vehicle operator may provide anindication of the completion of the vehicle trip using the client device110, the on-board computer 114, or the dedicated monitoring device (notshown). Where the trip is not complete at block 410, the client device110 proceeds to monitor and record the use of the vehicle at blocks412-424.

At block 412, the client device 110 determines the trip distance. Thismay include reading or updating a trip distance counter, comparing anodometer reading with an odometer reading recorded at the start of thetrip, or any other known technique. The trip distance is then comparedto a distance threshold set by the vehicle trip limitations at block414. Where the distance the vehicle 108 has traveled during the vehicletrip exceeds the distance threshold, the use of one vehicle use unit maybe recorded at block 424. Where the distance traveled is less than thedistance threshold, the client device 110 then determines the trip timeat block 416.

The trip time may be determined at block 416 as the time elapsed sincethe timestamp time at the start of the vehicle trip, the time of actualvehicle operation (e.g., the total time the vehicle engine is running orthe vehicle is in gear), or the time the vehicle operator is in thevehicle. The appropriate trip time must match the vehicle triplimitation regarding time. The trip time may be determined by anyappropriate means, including updating a trip time counter, comparing asystem clock reading with the timestamp time recorded at the start ofthe trip, or any other known technique. Where the duration of the tripexceeds the time threshold, the use of one vehicle use unit may berecorded at block 424. Where the trip time is less than the timethreshold, the client device 110 then determines the number of tripstops at block 420.

The trip stops may be determined at block 420 by any means, includingany the following or any combination of the following: determining thenumber of times the vehicle engine has been started or stopped duringone vehicle trip; determining the number of times the vehicle operatorhas entered or exited the vehicle 108 during one vehicle trip;determining the number of times the vehicle 108 has remained at the samelocation for a predetermined period of time (e.g., 5 minutes);determining the number of times the vehicle 108 has been located at ageographic location; determining the number of times the vehicle 108 hasentered or left a known roadway using GPS data from the GPS unit 206; orreceiving an indication of a vehicle stop from the vehicle operator.Where the trip stops exceed a stops threshold, the use of one vehicleuse unit may be recorded at block 424. Where the number of trip stops isless than the stops threshold, the client device 110 then continuesmonitoring the vehicle trip until the vehicle trip is complete.

When any of the vehicle trip limitations are reached and the use of avehicle use unit has been recorded at block 424, the client device 110may then reset the vehicle trip counters at block 406 in someembodiments. Alternatively, the trip distance, trip time, or trip stopsmay be determined in blocks 412, 416, and 420, respectively, based onthe most recent of either the start of the vehicle trip at block 402 orthe recordation of use of a vehicle use unit at block 424. In someembodiments, the client device 110 may communicate the use of a vehicleuse unit and information regarding the vehicle trip to the server 140via the network 130 upon each recordation of a use of a vehicle use unitat block 424. The server 140 may then record the use of a vehicle useunit and charge the vehicle insurance policy accordingly.

When the vehicle trip is complete at block 410, the client device 110may communicate information regarding the vehicle trip to the server 140via network 130. The server 140 records the use of one or more vehicleuse units and charges the vehicle use units to the trip-based vehicleinsurance policy at block 426. Additionally, information regarding thetrip may be associate with the timestamp created in block 404, as notedabove. The timestamp and associated information may be included in theinformation communicated by the client device 110 to the server 140 andrecorded by the server 140 in the system database 146.

Although the method 400 most directly applies to a trip-based vehicleinsurance policy with vehicle trip limitations on distance, time, andstops, it should be understood that a similar method could be applied toother trip-based vehicle insurance policies with more or fewer vehicletrip limitations. For example, a trip-based vehicle insurance policywith only vehicle trip limitations on distance and stops would lackblocks 416 and 418. Alternatively, the time threshold of block 418 mayinstead be set to an arbitrarily high value (e.g., 100 years) toeffectively prevent block 418 from triggering the use of a vehicle useunit.

FIG. 5 illustrates a flow diagram of a trip-based insurance monitoringmethod 500 that may operate to monitor vehicle use at block 316 to trackeach use of a vehicle wherein the cost of each vehicle trip isdetermined upon completion of the vehicle trip. The method 500 may beimplemented by the client device 110, on-board computer 114, dedicatedmonitoring device (not shown), or by the server 140 receivinginformation from any of these. For clarity, the following discussionrefers to an embodiment in which the client device 110 implements themethod 500 and communicates with the server 140 only at the completionof the vehicle trip, but it should be understood that any of thepreviously mentioned configurations may instead implement the method500.

The method 500 begins at block 502 when the client device 110 receivesan indication of the start of a vehicle trip, which may include any ofthe indications discussed above with respect to block 402. In alternateembodiments, the vehicle 108 may be continuously monitored, in whichcase the occurrence of a vehicle trip may be indicated at either thestart or end of the vehicle trip. Upon receiving an indication of thestart of the vehicle trip at block 502, the client device 110 may recorda time stamp associated with the start of the vehicle trip at block 504.The time stamp may include the date, time of day, location, or otherinformation related to the vehicle trip. The time stamp may be furtherassociated with additional information during or upon completion of thevehicle trip, including the following: distance traveled, duration ofthe vehicle trip, duration of vehicle operation during the vehicle trip(e.g., excluding stops), terminal location of the vehicle trip, unsafevehicle operation (e.g., hard braking, excessive acceleration, lateralswerving, etc.), weather conditions, vehicle occupants, or time,duration, and location of stops.

The client device 110 may then proceed to monitor the vehicle triplimitations while the vehicle trip is in progress and collect dataregarding the vehicle trip at block 506. The data may include dataregarding vehicle location, stops, speed, acceleration, indicators ofunsafe operation, or other information regarding vehicle operation. Thedata may further include information regarding weather conditions, roadconditions, operating conditions, or the vehicle operator. Data may becollected from a variety of sensors within or communicatively connectedto the client device 110 or the on-board computer 114. The sensors mayinclude any device capable of providing sensor data regarding thevehicle operator, vehicle location, vehicle operation, vehicle motion,or the vehicle's environment. The sensors may include the GPS unit 206,an accelerometer unit (not shown), an image capture unit (not shown), adistance sensor (not shown), a tachometer (not shown), a speedometer(not shown), or other vehicle sensors within the vehicle 108. Additionalsensors may be used to collect physiological data regarding the vehicleoperator (e.g., heart rate, telematics driving score, head movement,gaze direction, gaze duration, blink rate, galvanic skin response,etc.). Additional sensor data from sensors currently existing or laterdeveloped may also be used. The data may be collected and stored on theclient device 110 or may be communicated to the server 140 via thenetwork 130.

The client device 110 may determine whether the vehicle trip is completeat block 508. The vehicle trip may be determined to be complete upon theoccurrence of one or more of the following: the return of the vehicle108 to its starting location; the arrival of the vehicle 108 at anotherusual storage location; the engine of the vehicle 108 is shut off; thevehicle is taken out of an operational state to propel the vehicle 108;the vehicle operator exits the vehicle 108; the vehicle 108 is refueled.Additionally, or alternatively, the vehicle operator may provide anindication of the completion of the vehicle trip using the client device110, the on-board computer 114, or the dedicated monitoring device (notshown). Where the trip is not complete at block 510, the client device110 proceeds to collect data regarding the use of the vehicle at block506.

When the trip is complete at block 510, the client device 110 maycommunicate the information regarding the vehicle trip to the server140, which may determine the cost of the vehicle trip at block 512.Alternatively, the client device 110 may determine the cost of thevehicle trip and communicate the cost of the vehicle trip to the server140. The cost of the vehicle trip may be determined based upon thedistance, duration, stops, external conditions, or operation of thevehicle during the vehicle trip. Any of the vehicle trip limitationsmentioned above or other types of vehicle trip limitations may beincluded in the determination of the cost of the vehicle trip. Forexample, the cost of the vehicle trip may include a baseline cost basedon distance, adjustments for time of day and weather conditions, andsurcharges for unsafe vehicle operation (e.g., 0.05 vehicle use unitsfor each instance of hard braking, 0.07 vehicle use units for eachinstance of swerving, or 0.1 vehicle use units for each phone callduring the vehicle trip, etc.). Once the cost of the vehicle trip hasbeen determined at block 512, the server 140 may record the vehicle tripcost and, finally, charge or debit the vehicle insurance policy at block514. In some embodiments, charging or debiting the vehicle insurancepolicy may include recording the use of a whole or fractional number ofvehicle use units. In alternate embodiments, charging or debiting thevehicle insurance policy may include charging or debiting a monetarycost for the trip from the remaining balance of the initial monetaryvalue of the policy purchased by the customer.

Returning again to FIG. 3, the server 140 may determine the number ofremaining vehicle use units at block 318. Recording the vehicle tripsand usage of vehicle use units allows the server 140 to determine thenumber of vehicle use units remaining before the trip-based vehicleinsurance policy expires. In some embodiments, the remaining vehicle useunits may be determined by the client device 110, the on-board computer114, or the server 140 at block 318 by calculating the differencebetween the purchased vehicle use units and the recorded uses of vehicleuse units. Alternatively, the remaining vehicle use units may beestimated by the server 140 based on other know information, such aspast vehicle trip frequency and time elapsed since the previouspurchase. In various embodiments, the determination of remaining vehicleuse units may be performed periodically (e.g., weekly) or upon theoccurrence of each use of a vehicle use unit. In some embodiments,determination of the number of remaining vehicle use units maycorrespond to the determination of a remaining monetary value of thevehicle insurance policy.

The server 140 may then compare the remaining vehicle use unitsdetermined at block 318 with a predetermined threshold (e.g., two units,five units, ten units, etc.) at block 320. When the number of remainingvehicle use units falls below the predetermined threshold, the server140 may further determine at block 322 whether the vehicle insurancepolicy is configured to automatically renew with the purchase ofadditional vehicle use units. If the vehicle insurance policy is notconfigured to automatically renew, a notification alerting the vehicleoperator or customer may be generated by the server 140 and provided tothe vehicle operator or customer. More than one threshold may be used togenerate a plurality of notifications in some embodiments. When allvehicle use units purchased in a trip-based vehicle insurance policyhave been used, the policy may expire, or a portion of the policy thatis time-based or distance-based may remain in force according to thepolicy terms.

When the server 140 determines that the vehicle insurance policy isconfigured to automatically renew upon reaching the predeterminedthreshold at block 322, the server 140 may then facilitate an additionalpurchase of vehicle use units at block 326 according to the same termsas previously in effect. The purchase may be facilitated by any of thevarious known techniques, including receiving an electronic payment fromthe user, receiving a purchase order to be invoiced, or generating apurchase order number for the customer to use in confirming the purchaseat a physical office location, by telephone, or otherwise. In someembodiments, a financial account (e.g., a checking account at a bank) ora revolving account (e.g., a credit card) may be connected to thevehicle insurance policy, and the server 140 may charge or debit thecost of the additional purchase to the account. Upon confirmation orcompletion of the order, the server 140 may provide the user withadditional required or optional documentation regarding the purchasedvehicle insurance policy, including proof of insurance. The server 140may then continue to monitor vehicle use at block 316.

Throughout this specification, plural instances may implementcomponents, operations, or structures described as a single instance.Although individual operations of one or more methods are illustratedand described as separate operations, one or more of the individualoperations may be performed concurrently, and nothing requires that theoperations be performed in the order illustrated. Structures andfunctionality presented as separate components in example configurationsmay be implemented as a combined structure or component. Similarly,structures and functionality presented as a single component may beimplemented as separate components. These and other variations,modifications, additions, and improvements fall within the scope of thesubject matter herein.

Additionally, certain embodiments are described herein as includinglogic or a number of routines, subroutines, applications, orinstructions. These may constitute either software (code embodied on anon-transitory, tangible machine-readable medium) or hardware. Inhardware, the routines, etc., are tangible units capable of performingcertain operations and may be configured or arranged in a certainmanner. In example embodiments, one or more computer systems (e.g., astandalone, client or server computer system) or one or more hardwaremodules of a computer system (e.g., a processor or a group ofprocessors) may be configured by software (e.g., an application orapplication portion) as a hardware module that operates to performcertain operations as described herein.

In various embodiments, a hardware module may be implementedmechanically or electronically. For example, a hardware module maycomprise dedicated circuitry or logic that is permanently configured(e.g., as a special-purpose processor, such as a field programmable gatearray (FPGA) or an application-specific integrated circuit (ASIC) toperform certain operations. A hardware module may also compriseprogrammable logic or circuitry (e.g., as encompassed within ageneral-purpose processor or other programmable processor) that istemporarily configured by software to perform certain operations. Itwill be appreciated that the decision to implement a hardware modulemechanically, in dedicated and permanently configured circuitry, or intemporarily configured circuitry (e.g., configured by software) may bedriven by cost and time considerations.

Accordingly, the term “hardware module” should be understood toencompass a tangible entity, be that an entity that is physicallyconstructed, permanently configured (e.g., hardwired), or temporarilyconfigured (e.g., programmed) to operate in a certain manner or toperform certain operations described herein. Considering embodiments inwhich hardware modules are temporarily configured (e.g., programmed),each of the hardware modules need not be configured or instantiated atany one instance in time. For example, where the hardware modulescomprise a general-purpose processor configured using software, thegeneral-purpose processor may be configured as respective differenthardware modules at different times. Software may accordingly configurea processor, for example, to constitute a particular hardware module atone instance of time and to constitute a different hardware module at adifferent instance of time.

Hardware modules can provide information to, and receive informationfrom, other hardware modules. Accordingly, the described hardwaremodules may be regarded as being communicatively coupled. Where multipleof such hardware modules exist contemporaneously, communications may beachieved through signal transmission (e.g., over appropriate circuitsand buses) that connect the hardware modules. In embodiments in whichmultiple hardware modules are configured or instantiated at differenttimes, communications between such hardware modules may be achieved, forexample, through the storage and retrieval of information in memorystructures to which the multiple hardware modules have access. Forexample, one hardware module may perform an operation and store theoutput of that operation in a memory device to which it iscommunicatively coupled. A further hardware module may then, at a latertime, access the memory device to retrieve and process the storedoutput. Hardware modules may also initiate communications with input oroutput devices, and can operate on a resource (e.g., a collection ofinformation).

The various operations of example methods described herein may beperformed, at least partially, by one or more processors that aretemporarily configured (e.g., by software) or permanently configured toperform the relevant operations. Whether temporarily or permanentlyconfigured, such processors may constitute processor-implemented modulesthat operate to perform one or more operations or functions. The modulesreferred to herein may, in some example embodiments, compriseprocessor-implemented modules.

Similarly, the methods or routines described herein may be at leastpartially processor-implemented. For example, at least some of theoperations of a method may be performed by one or more processors orprocessor-implemented hardware modules. The performance of certain ofthe operations may be distributed among the one or more processors, notonly residing within a single machine, but deployed across a number ofmachines. In some example embodiments, the processor or processors maybe located in a single location (e.g., within a home environment, anoffice environment or as a server farm), while in other embodiments theprocessors may be distributed across a number of locations.

The performance of certain of the operations may be distributed amongthe one or more processors, not only residing within a single machine,but deployed across a number of machines. In some example embodiments,the one or more processors or processor-implemented modules may belocated in a single geographic location (e.g., within a homeenvironment, an office environment, or a server farm). In other exampleembodiments, the one or more processors or processor-implemented modulesmay be distributed across a number of geographic locations.

Unless specifically stated otherwise, discussions herein using wordssuch as “processing,” “computing,” “calculating,” “determining,”“presenting,” “displaying,” or the like may refer to actions orprocesses of a machine (e.g., a computer) that manipulates or transformsdata represented as physical (e.g., electronic, magnetic, or optical)quantities within one or more memories (e.g., volatile memory,non-volatile memory, or a combination thereof), registers, or othermachine components that receive, store, transmit, or displayinformation.

As used herein any reference to “one embodiment” or “an embodiment”means that a particular element, feature, structure, or characteristicdescribed in connection with the embodiment is included in at least oneembodiment. The appearances of the phrase “in one embodiment” in variousplaces in the specification are not necessarily all referring to thesame embodiment.

Some embodiments may be described using the expression “coupled” and“connected” along with their derivatives. For example, some embodimentsmay be described using the term “coupled” to indicate that two or moreelements are in direct physical or electrical contact. The term“coupled,” however, may also mean that two or more elements are not indirect contact with each other, but yet still co-operate or interactwith each other. The embodiments are not limited in this context.

As used herein, the terms “comprises,” “comprising,” “includes,”“including,” “has,” “having” or any other variation thereof, areintended to cover a non-exclusive inclusion. For example, a process,method, article, or apparatus that comprises a list of elements is notnecessarily limited to only those elements but may include otherelements not expressly listed or inherent to such process, method,article, or apparatus. Further, unless expressly stated to the contrary,“or” refers to an inclusive or and not to an exclusive or. For example,a condition A or B is satisfied by any one of the following: A is true(or present) and B is false (or not present), A is false (or notpresent) and B is true (or present), and both A and B are true (orpresent).

In addition, use of the “a” or “an” are employed to describe elementsand components of the embodiments herein. This is done merely forconvenience and to give a general sense of the description. Thisdescription, and the claims that follow, should be read to include oneor at least one and the singular also includes the plural unless it isobvious that it is meant otherwise.

This detailed description is to be construed as exemplary only and doesnot describe every possible embodiment, as describing every possibleembodiment would be impractical, if not impossible. One could implementnumerous alternate embodiments, using either current technology ortechnology developed after the filing date of this application.

Upon reading this disclosure, those of skill in the art will appreciatestill additional alternative structural and functional designs forsystem and a method for assigning mobile device data to a vehiclethrough the disclosed principles herein. Thus, while particularembodiments and applications have been illustrated and described, it isto be understood that the disclosed embodiments are not limited to theprecise construction and components disclosed herein. Variousmodifications, changes and variations, which will be apparent to thoseskilled in the art, may be made in the arrangement, operation anddetails of the method and apparatus disclosed herein without departingfrom the spirit and scope defined in the appended claims.

The particular features, structures, or characteristics of any specificembodiment may be combined in any suitable manner and in any suitablecombination with one or more other embodiments, including the use ofselected features without corresponding use of other features. Inaddition, many modifications may be made to adapt a particularapplication, situation or material to the essential scope and spirit ofthe present invention. It is to be understood that other variations andmodifications of the embodiments of the present invention described andillustrated herein are possible in light of the teachings herein and areto be considered part of the spirit and scope of the present invention.By way of example, and not limitation, the present disclosurecontemplates at least the following aspects:

1. A computer-implemented method for offering vehicle insurance for avehicle, comprising: receiving, by one or more processors, a vehicleidentifier that identifies the vehicle and a vehicle operator identifierthat identifies a vehicle operator; determining, by one or moreprocessors, a cost per vehicle use unit based at least in part on thevehicle identifier and the vehicle operator identifier; generating, byone or more processors, at least one vehicle insurance policy based atleast in part on the cost per vehicle use unit; and providing, by one ormore processors, an option to purchase the vehicle insurance policy to acustomer associated with the vehicle.

2. The method according to aspect 1, wherein the cost per vehicle useunit comprises a cost associated with a vehicle trip, the vehicle tripincluding at least one of: each round trip from and back to a location;each time an engine of the vehicle is started; each time the engine ofthe vehicle is shut off; each time the engine of the vehicle is put intoan operational state to propel the vehicle; each time the engine of thevehicle is taken out of an operational state to propel the vehicle; eachtime the vehicle operator enters the vehicle; each time the vehicleoperator exits the vehicle; each time the vehicle arrives at ageographic location; each time the vehicle leaves a geographic location;or each time the vehicle is refueled.

3. The method according to either aspect 1 or aspect 2, wherein the costper vehicle use unit further comprises a cost associated with a vehicletrip limitation, the vehicle trip limitation including at least one of:a predetermined maximum distance traveled by the vehicle in one vehicletrip; a predetermined maximum duration of vehicle operation within onevehicle trip; a predetermined maximum duration during which the engineof the vehicle is running in one vehicle trip; a predetermined maximumnumber of times the engine of the vehicle is started or shut off in onevehicle trip; a predetermined number of times the vehicle operator enteror exits the vehicle in one vehicle trip; a predetermined number oftimes the vehicle is near a geographic location; a predetermined maximumspeed of the vehicle during the vehicle trip; a predetermined maximumrevolutions per minute of the engine of the vehicle during the vehicletrip; a predetermined maximum lateral acceleration of the vehicle duringthe vehicle trip; a predetermined maximum longitudinal acceleration ofthe vehicle during the vehicle trip; a predetermined maximum number ofoccupants within the vehicle during the vehicle trip; an indication ofunsafe vehicle operation; or an indication of hazardous weatherconditions.

4. The method according to any one of the preceding aspects, furthercomprising: receiving, by one or more processors, a selection by thecustomer of the vehicle insurance policy; facilitating, by one or moreprocessors, a purchase transaction with the customer for the selectedvehicle insurance policy; receiving, by one or more processors, a signalindicating an occurrence of the vehicle trip; and recording, by one ormore processors, a record of the occurrence of the vehicle trip.

5. The method according to any one of the preceding aspects, whereinrecording the record of the occurrence of the vehicle trip furthercomprises recording, by one or more processors, a timestamp of theoccurrence, the timestamp including at least one of: a start time of thevehicle trip, an end time of the vehicle trip, a distance traveled, astarting location of the vehicle trip, a terminal location of thevehicle trip, an indication of unsafe vehicle operation, an indicationof weather conditions, or an indication of occupants of the vehicle.

6. The method according to any one of the preceding aspects, furthercomprising: determining, by one or more processors, a number ofremaining vehicle use units in the purchased vehicle insurance policy;and facilitating, by one or more processors, an additional purchasetransaction with the customer to purchase additional vehicle tripswithout further action by the customer when the number of remainingvehicle use units falls below a predetermined threshold.

7. The method according to any one of the preceding aspects, whereinproviding the option to purchase the vehicle insurance policy to thecustomer further comprises: providing, by one or more processors, anoption to purchase at least one type of vehicle insurance coverage, andproviding, by one or more processors, an option to purchase at least onequantity of vehicle use units.

8. The method according to any one of the preceding aspects, furthercomprising: receiving, by one or more processors, a selection by thecustomer of the vehicle insurance policy; and facilitating, by one ormore processors, a purchase transaction with the customer for theselected vehicle insurance policy.

9. The method according to any one of the preceding aspects, whereinpresenting the option to purchase the vehicle insurance policy to thecustomer further comprises: identifying, by one or more processors, anexisting insurance policy associated with the customer; and providing tothe customer, by one or more processors, an option to supplement theexisting insurance policy with the vehicle insurance policy.

10. The method according to any one of the preceding aspects, furthercomprising receiving, by one or more processors, a vehicle useidentifier that identifies information regarding a recurring use of thevehicle by the vehicle operator, the information including at least oneof: a parking location, a destination location, a route, a type of use,a time of use, a pattern of unsafe vehicle operation, a number ofoccupants within the vehicle, or a cargo; wherein the cost per vehicleuse unit is based, at least in part, on the vehicle use identifier.

11. A computer system for offering vehicle insurance for a vehicle,comprising: a communication module adapted to communicate data; aprogram memory adapted to store non-transitory computer executableinstructions; and at least one processor adapted to interface with thecommunication module, wherein the processor is configured to execute thenon-transitory computer executable instructions to cause the computersystem to: receive a vehicle identifier that identifies the vehicle anda vehicle operator identifier that identifies a vehicle operator;determine a cost per vehicle use unit based at least in part on thevehicle identifier and the vehicle operator identifier; generate atleast one vehicle insurance policy based at least in part on the costper vehicle use unit; and provide, to a customer associated with thevehicle via the communication module, an option to purchase the vehicleinsurance policy to a customer associated with the vehicle.

12. The computer system according to aspect 11, wherein the cost pervehicle use unit comprises a cost associated with a vehicle trip, thevehicle trip including at least one of: each round trip from and back toa location; each time an engine of the vehicle is started; each time theengine of the vehicle is shut off; each time the engine of the vehicleis put into an operational state to propel the vehicle; each time theengine of the vehicle is taken out of an operational state to propel thevehicle; each time the vehicle operator enters the vehicle; each timethe vehicle operator exits the vehicle; each time the vehicle arrives ata geographic location; each time the vehicle leaves a geographiclocation; or each time the vehicle is refueled.

13. The computer system according to either aspect 11 or aspect 12,wherein the cost per vehicle use unit further comprises a costassociated with a vehicle trip limitation, the vehicle trip limitationincluding at least one of: a predetermined maximum distance traveled bythe vehicle in one vehicle trip; a predetermined maximum duration ofvehicle operation within one vehicle trip; a predetermined maximumduration during which the engine of the vehicle is running in onevehicle trip; a predetermined maximum number of times the engine of thevehicle is started or shut off in one vehicle trip; a predeterminednumber of times the vehicle operator enter or exits the vehicle in onevehicle trip; a predetermined number of times the vehicle is near ageographic location; a predetermined maximum speed of the vehicle duringthe vehicle trip; a predetermined maximum revolutions per minute of theengine of the vehicle during the vehicle trip; a predetermined maximumlateral acceleration of the vehicle during the vehicle trip; apredetermined maximum longitudinal acceleration of the vehicle duringthe vehicle trip; a predetermined maximum number of occupants within thevehicle during the vehicle trip; an indication of unsafe vehicleoperation; or an indication of hazardous weather conditions.

14. The computer system according to any of aspects 11-13, wherein theexecutable instructions further cause the computer system to: receive,from the customer via the communication module, a selection of thevehicle insurance policy; facilitate a purchase transaction with thecustomer for the vehicle insurance policy; receive, via thecommunication module, a signal indicating an occurrence of the vehicletrip; and record a timestamp of the occurrence of the vehicle trip, thetimestamp comprising at least one of: a start time of the vehicle trip,an end time of the vehicle trip, a distance traveled, a startinglocation of the vehicle trip, a terminal location of the vehicle trip,an indication of unsafe vehicle operation, an indication of weatherconditions, or an indication of occupants of the vehicle.

15. The computer system according to any of aspects 11-14, wherein theexecutable instructions that cause the computer system to receive thesignal indicating the occurrence of the vehicle trip further compriseinstructions that cause the computer system to receive, via thecommunication module, a signal from a sensor configured to generate thesignal indicating the occurrence of the vehicle trip.

16. A tangible, non-transitory computer-readable medium storinginstructions for offering vehicle insurance for a vehicle that whenexecuted by at least one processor of a computer system cause thecomputer system to: receive a vehicle identifier that identifies thevehicle and a vehicle operator identifier that identifies a vehicleoperator; determine a cost per vehicle use unit based at least in parton the vehicle identifier and the vehicle operator identifier; generateat least one vehicle insurance policy based at least in part on the costper vehicle use unit; and provide, to a customer associated with thevehicle, an option to purchase the vehicle insurance policy.

17. The tangible, non-transitory computer-readable medium according toaspect 16, wherein the cost per vehicle use unit comprises a costassociated with a vehicle trip, the vehicle trip including at least oneof: each round trip from and back to a location; each time an engine ofthe vehicle is started; each time the engine of the vehicle is shut off;each time the engine of the vehicle is put into an operational state topropel the vehicle; each time the engine of the vehicle is taken out ofan operational state to propel the vehicle; each time the vehicleoperator enters the vehicle; each time the vehicle operator exits thevehicle; each time the vehicle arrives at a geographic location; eachtime the vehicle leaves a geographic location; or each time the vehicleis refueled.

18. The tangible, non-transitory computer-readable medium according toeither of aspect 16 or aspect 17, wherein the cost per vehicle use unitfurther comprises a cost associated with a vehicle trip limitation, thevehicle trip limitation including at least one of: a predeterminedmaximum distance traveled by the vehicle in one vehicle trip; apredetermined maximum duration of vehicle operation within one vehicletrip; a predetermined maximum duration during which the engine of thevehicle is running in one vehicle trip; a predetermined maximum numberof times the engine of the vehicle is started or shut off in one vehicletrip; a predetermined number of times the vehicle operator enter orexits the vehicle in one vehicle trip; a predetermined number of timesthe vehicle is near a geographic location; a predetermined maximum speedof the vehicle during the vehicle trip; a predetermined maximumrevolutions per minute of the engine of the vehicle during the vehicletrip; a predetermined maximum lateral acceleration of the vehicle duringthe vehicle trip; a predetermined maximum longitudinal acceleration ofthe vehicle during the vehicle trip; a predetermined maximum number ofoccupants within the vehicle during the vehicle trip; an indication ofunsafe vehicle operation; or an indication of hazardous weatherconditions.

19. The tangible, non-transitory computer-readable medium according toany of aspects 16-18, wherein the executable instructions furthercomprise executable instructions that when executed by the at least oneprocessor cause the computer system to: receive a selection of thevehicle insurance policy from the customer; facilitate a purchasetransaction with the customer for the vehicle insurance policy; receivea signal indicating an occurrence of the vehicle trip; and record atimestamp of the occurrence of the vehicle trip, the timestampcomprising at least one of: a start time of the vehicle trip, an endtime of the vehicle trip, a distance traveled, a starting location ofthe vehicle trip, a terminal location of the vehicle trip, an indicationof unsafe vehicle operation, an indication of weather conditions, or anindication of occupants of the vehicle.

20. The tangible, non-transitory computer-readable medium according toany of aspects 16-19, wherein the executable instructions that whenexecuted by the at least one processor cause the computer system toprovide the option to purchase the vehicle insurance policy furthercomprise executable instructions that when executed by the at least oneprocessor cause the computer system to: identify an existing insurancepolicy associated with the customer; and provide, to the customer, anoption to supplement the existing insurance policy with the vehicleinsurance policy.

What is claimed is:
 1. A computer-implemented method for offeringvehicle insurance for a vehicle, comprising: receiving, by one or moreprocessors, a vehicle identifier that identifies the vehicle and avehicle operator identifier that identifies a vehicle operator;determining, by one or more processors, a cost per vehicle use unitbased at least in part on the vehicle identifier and the vehicleoperator identifier; generating, by one or more processors, at least onevehicle insurance policy based at least in part on the cost per vehicleuse unit; and providing, by one or more processors, an option topurchase the vehicle insurance policy to a customer associated with thevehicle.
 2. The method of claim 1, wherein the cost per vehicle use unitcomprises a cost associated with a vehicle trip, the vehicle tripincluding at least one of: each round trip from and back to a location;each time an engine of the vehicle is started; each time the engine ofthe vehicle is shut off; each time the engine of the vehicle is put intoan operational state to propel the vehicle; each time the engine of thevehicle is taken out of an operational state to propel the vehicle; eachtime the vehicle operator enters the vehicle; each time the vehicleoperator exits the vehicle; each time the vehicle arrives at ageographic location; each time the vehicle leaves a geographic location;or each time the vehicle is refueled.
 3. The method of claim 2, whereinthe cost per vehicle use unit further comprises a cost associated with avehicle trip limitation, the vehicle trip limitation including at leastone of: a predetermined maximum distance traveled by the vehicle in onevehicle trip; a predetermined maximum duration of vehicle operationwithin one vehicle trip; a predetermined maximum duration during whichthe engine of the vehicle is running in one vehicle trip; apredetermined maximum number of times the engine of the vehicle isstarted or shut off in one vehicle trip; a predetermined number of timesthe vehicle operator enter or exits the vehicle in one vehicle trip; apredetermined number of times the vehicle is near a geographic location;a predetermined maximum speed of the vehicle during the vehicle trip; apredetermined maximum revolutions per minute of the engine of thevehicle during the vehicle trip; a predetermined maximum lateralacceleration of the vehicle during the vehicle trip; a predeterminedmaximum longitudinal acceleration of the vehicle during the vehicletrip; a predetermined maximum number of occupants within the vehicleduring the vehicle trip; an indication of unsafe vehicle operation; oran indication of hazardous weather conditions.
 4. The method of claim 2,further comprising: receiving, by one or more processors, a selection bythe customer of the vehicle insurance policy; facilitating, by one ormore processors, a purchase transaction with the customer for theselected vehicle insurance policy; receiving, by one or more processors,a signal indicating an occurrence of the vehicle trip; and recording, byone or more processors, a record of the occurrence of the vehicle trip.5. The method of claim 4, wherein recording the record of the occurrenceof the vehicle trip further comprises recording, by one or moreprocessors, a timestamp of the occurrence, the timestamp including atleast one of: a start time of the vehicle trip, an end time of thevehicle trip, a distance traveled, a starting location of the vehicletrip, a terminal location of the vehicle trip, an indication of unsafevehicle operation, an indication of weather conditions, or an indicationof occupants of the vehicle.
 6. The method of claim 4, furthercomprising: determining, by one or more processors, a number ofremaining vehicle use units in the purchased vehicle insurance policy;and facilitating, by one or more processors, an additional purchasetransaction with the customer to purchase additional vehicle tripswithout further action by the customer when the number of remainingvehicle use units falls below a predetermined threshold.
 7. The methodof claim 1, wherein providing the option to purchase the vehicleinsurance policy to the customer further comprises: providing, by one ormore processors, an option to purchase at least one type of vehicleinsurance coverage, and providing, by one or more processors, an optionto purchase at least one quantity of vehicle use units.
 8. The method ofclaim 7, further comprising: receiving, by one or more processors, aselection by the customer of the vehicle insurance policy; andfacilitating, by one or more processors, a purchase transaction with thecustomer for the selected vehicle insurance policy.
 9. The method ofclaim 1, wherein presenting the option to purchase the vehicle insurancepolicy to the customer further comprises: identifying, by one or moreprocessors, an existing insurance policy associated with the customer;and providing to the customer, by one or more processors, an option tosupplement the existing insurance policy with the vehicle insurancepolicy.
 10. The method of claim 1, further comprising receiving, by oneor more processors, a vehicle use identifier that identifies informationregarding a recurring use of the vehicle by the vehicle operator, theinformation including at least one of: a parking location, a destinationlocation, a route, a type of use, a time of use, a pattern of unsafevehicle operation, a number of occupants within the vehicle, or a cargo;wherein the cost per vehicle use unit is based, at least in part, on thevehicle use identifier.
 11. A computer system for offering vehicleinsurance for a vehicle, comprising: a communication module adapted tocommunicate data; a program memory adapted to store non-transitorycomputer executable instructions; and at least one processor adapted tointerface with the communication module, wherein the processor isconfigured to execute the non-transitory computer executableinstructions to cause the computer system to: receive a vehicleidentifier that identifies the vehicle and a vehicle operator identifierthat identifies a vehicle operator; determine a cost per vehicle useunit based at least in part on the vehicle identifier and the vehicleoperator identifier; generate at least one vehicle insurance policybased at least in part on the cost per vehicle use unit; and provide, toa customer associated with the vehicle via the communication module, anoption to purchase the vehicle insurance policy to a customer associatedwith the vehicle.
 12. The computer system of claim 11, wherein the costper vehicle use unit comprises a cost associated with a vehicle trip,the vehicle trip including at least one of: each round trip from andback to a location; each time an engine of the vehicle is started; eachtime the engine of the vehicle is shut off; each time the engine of thevehicle is put into an operational state to propel the vehicle; eachtime the engine of the vehicle is taken out of an operational state topropel the vehicle; each time the vehicle operator enters the vehicle;each time the vehicle operator exits the vehicle; each time the vehiclearrives at a geographic location; each time the vehicle leaves ageographic location; or each time the vehicle is refueled.
 13. Thecomputer system of claim 12, wherein the cost per vehicle use unitfurther comprises a cost associated with a vehicle trip limitation, thevehicle trip limitation including at least one of: a predeterminedmaximum distance traveled by the vehicle in one vehicle trip; apredetermined maximum duration of vehicle operation within one vehicletrip; a predetermined maximum duration during which the engine of thevehicle is running in one vehicle trip; a predetermined maximum numberof times the engine of the vehicle is started or shut off in one vehicletrip; a predetermined number of times the vehicle operator enter orexits the vehicle in one vehicle trip; a predetermined number of timesthe vehicle is near a geographic location; a predetermined maximum speedof the vehicle during the vehicle trip; a predetermined maximumrevolutions per minute of the engine of the vehicle during the vehicletrip; a predetermined maximum lateral acceleration of the vehicle duringthe vehicle trip; a predetermined maximum longitudinal acceleration ofthe vehicle during the vehicle trip; a predetermined maximum number ofoccupants within the vehicle during the vehicle trip; an indication ofunsafe vehicle operation; or an indication of hazardous weatherconditions.
 14. The computer system of claim 12, wherein the executableinstructions further cause the computer system to: receive, from thecustomer via the communication module, a selection of the vehicleinsurance policy; facilitate a purchase transaction with the customerfor the vehicle insurance policy; receive, via the communication module,a signal indicating an occurrence of the vehicle trip; and record atimestamp of the occurrence of the vehicle trip, the timestampcomprising at least one of: a start time of the vehicle trip, an endtime of the vehicle trip, a distance traveled, a starting location ofthe vehicle trip, a terminal location of the vehicle trip, an indicationof unsafe vehicle operation, an indication of weather conditions, or anindication of occupants of the vehicle.
 15. The computer system of claim14, wherein the executable instructions that cause the computer systemto receive the signal indicating the occurrence of the vehicle tripfurther comprise instructions that cause the computer system to receive,via the communication module, a signal from a sensor configured togenerate the signal indicating the occurrence of the vehicle trip.
 16. Atangible, non-transitory computer-readable medium storing instructionsfor offering vehicle insurance for a vehicle that when executed by atleast one processor of a computer system cause the computer system to:receive a vehicle identifier that identifies the vehicle and a vehicleoperator identifier that identifies a vehicle operator; determine a costper vehicle use unit based at least in part on the vehicle identifierand the vehicle operator identifier; generate at least one vehicleinsurance policy based at least in part on the cost per vehicle useunit; and provide, to a customer associated with the vehicle, an optionto purchase the vehicle insurance policy.
 17. The tangible,non-transitory computer-readable medium of claim 16, wherein the costper vehicle use unit comprises a cost associated with a vehicle trip,the vehicle trip including at least one of: each round trip from andback to a location; each time an engine of the vehicle is started; eachtime the engine of the vehicle is shut off; each time the engine of thevehicle is put into an operational state to propel the vehicle; eachtime the engine of the vehicle is taken out of an operational state topropel the vehicle; each time the vehicle operator enters the vehicle;each time the vehicle operator exits the vehicle; each time the vehiclearrives at a geographic location; each time the vehicle leaves ageographic location; or each time the vehicle is refueled.
 18. Thetangible, non-transitory computer-readable medium of claim 16, whereinthe cost per vehicle use unit further comprises a cost associated with avehicle trip limitation, the vehicle trip limitation including at leastone of: a predetermined maximum distance traveled by the vehicle in onevehicle trip; a predetermined maximum duration of vehicle operationwithin one vehicle trip; a predetermined maximum duration during whichthe engine of the vehicle is running in one vehicle trip; apredetermined maximum number of times the engine of the vehicle isstarted or shut off in one vehicle trip; a predetermined number of timesthe vehicle operator enter or exits the vehicle in one vehicle trip; apredetermined number of times the vehicle is near a geographic location;a predetermined maximum speed of the vehicle during the vehicle trip; apredetermined maximum revolutions per minute of the engine of thevehicle during the vehicle trip; a predetermined maximum lateralacceleration of the vehicle during the vehicle trip; a predeterminedmaximum longitudinal acceleration of the vehicle during the vehicletrip; a predetermined maximum number of occupants within the vehicleduring the vehicle trip; an indication of unsafe vehicle operation; oran indication of hazardous weather conditions.
 19. The tangible,non-transitory computer-readable medium of claim 17, wherein theexecutable instructions further comprise executable instructions thatwhen executed by the at least one processor cause the computer systemto: receive a selection of the vehicle insurance policy from thecustomer; facilitate a purchase transaction with the customer for thevehicle insurance policy; receive a signal indicating an occurrence ofthe vehicle trip; and record a timestamp of the occurrence of thevehicle trip, the timestamp comprising at least one of: a start time ofthe vehicle trip, an end time of the vehicle trip, a distance traveled,a starting location of the vehicle trip, a terminal location of thevehicle trip, an indication of unsafe vehicle operation, an indicationof weather conditions, or an indication of occupants of the vehicle. 20.The tangible, non-transitory computer-readable medium of claim 16,wherein the executable instructions that when executed by the at leastone processor cause the computer system to provide the option topurchase the vehicle insurance policy further comprise executableinstructions that when executed by the at least one processor cause thecomputer system to: identify an existing insurance policy associatedwith the customer; and provide, to the customer, an option to supplementthe existing insurance policy with the vehicle insurance policy.